<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Concept: 需求类型</title>
<meta name="uma.type" content="Concept">
<meta name="uma.name" content="types_of_requirements">
<meta name="uma.presentationName" content="需求类型">
<meta name="element_type" content="concept">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var backPath = './../../../';
					var imgPath = './../../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo,  '', false, false, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top"><a name="Top"></a>
<div id="page-guid" value="5.360970653483052E-305"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Concept: 需求类型</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../../images/concept.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">需求类型只是一类需求，它使团队可以将大量的需求组织为有意义的、更易于管理的组。在项目中建立不同类型的需求有助于团队成员将需求分类并使通信更为清晰。</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Related Elements</th><td class="sectionTableCell">
<ul>
<li>
<a href="./../../../rup/workproducts/rup_actor_1F9CE9.html" guid="{0EEBBA43-F5C6-4594-9F06-65D99F7556DF}">参与者</a>
</li>
<li>
<a href="./../../../rup/workproducts/rup_software_requirement_32CECE14.html" guid="{BB502500-EEEC-4BDE-8697-186666D6D5B3}">软件需求</a>
</li>
<li>
<a href="./../../../rup/workproducts/rup_software_requirements_specification_934E66F.html" guid="{BE8165DC-BAF2-4237-B27D-F2A037023364}">软件需求规约</a>
</li>
<li>
<a href="./../../../rup/roles/rup_system_analyst_C3C9C9AC.html" guid="{F1F206DF-3AA0-4AC0-92EF-8E4A01B6C5B5}">系统分析人员</a>
</li>
<li>
<a href="./../../../rup/domains/requirements_58267518.html" guid="_KVkLoN7HEdm8G6yT7-Wdqw">需求</a>
</li>
<li>
<a href="./../../../rup/workproducts/rup_requirements_management_plan_1CA2ED11.html" guid="{53CFF11F-D0DB-4C92-B4D8-90D46B0EE3DF}">需求管理计划</a>
</li>
<li>
<a href="./../../../rup/workproducts/rup_requirements_attributes_EFE5ABAC.html" guid="{D0E2E7A1-4179-470E-AA18-419D5FEA275D}">需求属性</a>
</li>
<li>
<a href="./../../../rup/workproducts/rup_usecase_A5D30E62.html" guid="{B1526BC5-E346-42CB-A08A-3C0D7F382407}">用例</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Main Description</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td class="sectionTableSingleCell"><a id="Top" name="Top"></a><a key="需求（requirements）" text="类型" name="XE_requirements__types_of" id="XE_requirements__types_of" class="index"></a> 
<p>
    传统上，需求可视为<a class="elementLinkWithType" href="./../../../rup/guidances/concepts/requirements_62E28784.html" guid="4.582668643506599E-305">Concept: 需求</a>中所述类别之一的文本声明。每个需求都陈述了“系统必须遵循的条件或能力”。
</p>
<p>
    为执行有效的<a class="elementLink" href="./../../../rup/guidances/concepts/requirements_management_8067CA83.html" guid="8.93441552545224E-307">需求管理</a>，我们已经知道将我们作为需求维护的范围扩展到不再仅限于详细“软件需求”，这是有帮助的。我们引入<b>需求类型</b>的概念以帮助区分需求的不同抽象级别和用途。&nbsp;
</p>
<p align="center">
    <map id="FPMap0" name="FPMap0">
        <area shape="rect" alt="软件需求规约" coords="110,72,181,100" href="./../../../rup/workproducts/rup_software_requirements_specification_934E66F.html" guid="{BE8165DC-BAF2-4237-B27D-F2A037023364}"></area>
        <area shape="rect" alt="测试套件" coords="185,220,263,292" href="./../../../rup/workproducts/rup_test_suite_DA8938D2.html" guid="{33DE37A2-ECFE-483B-934B-629F5802F87C}"></area>
        <area shape="rect" alt="设计模型" coords="74,220,158,292" href="./../../../rup/workproducts/rup_design_model_2830034D.html" guid="{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}"></area>
        <area shape="rect" alt="补充规约" coords="237,104,325,173" href="./../../../rup/workproducts/rup_supplementary_specification_F5ACAA22.html" guid="{B16C2941-791C-44E6-B353-354109B5C9DE}"></area>
        <area shape="rect" alt="用例模型" coords="116,104,208,173" href="./../../../rup/workproducts/rup_usecase_model_EF15E534.html" guid="{9C66F2EC-EDEB-4369-9AFB-04B9E7CBCB8E}"></area>
        <area shape="rect" alt="项目干系人请求" coords="1,89,61,158" href="./../../../rup/workproducts/rup_stakeholder_requests_A89D2BF9.html" guid="{75F38765-E25B-4459-907E-77F429652C0F}"></area>
        <area shape="rect" alt="愿景" coords="193,20,248,78" href="./../../../rup/workproducts/rup_vision_2D6D6F1.html" guid="{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}"></area>
    </map><img height="292" alt="概念：需求" src="./../../../rup/guidances/concepts/resources/co_tracg.gif" width="487" usemap="#fpmap0" border="0" />
</p>
<p>
    我们可能想要跟踪来自<a class="elementLinkWithUserText" href="./../../../rup/roles/rup_stakeholder_1011D446.html" guid="{7A4262EA-AB5B-431E-BB4A-3822FBF7F239}">项目干系人</a>的含糊的“愿望”以及正式的<a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_stakeholder_requests_A89D2BF9.html" guid="{75F38765-E25B-4459-907E-77F429652C0F}">请求</a>，以确保能了解它们的处理情况。 <a class="elementLink" href="./../../../rup/workproducts/rup_vision_2D6D6F1.html" guid="{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}">愿景</a>文档帮助我们跟踪系统的关键“用户需要”和“特性”。<a class="elementLink" href="./../../../rup/workproducts/rup_usecase_model_EF15E534.html" guid="{9C66F2EC-EDEB-4369-9AFB-04B9E7CBCB8E}">用例模型</a>是一种表达详细的功能“软件需求”的有效方法，因此可能需要跟踪这些<a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_usecase_A5D30E62.html" guid="{B1526BC5-E346-42CB-A08A-3C0D7F382407}">用例</a>并将其作为需求来维护，并且可能需要跟踪和维护用例属性中的个别陈述，这些陈述声明“系统必须遵循的条件或能力”。<a class="elementLink" href="./../../../rup/workproducts/rup_supplementary_specification_F5ACAA22.html" guid="{B16C2941-791C-44E6-B353-354109B5C9DE}">补充规约</a>可以包含其他“软件需求”，例如系统上的设计约束或者法律或规章要求。对于软件需求的完整定义，<a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_usecase_A5D30E62.html" guid="{B1526BC5-E346-42CB-A08A-3C0D7F382407}">用例</a>和<a class="elementLink" href="./../../../rup/workproducts/rup_supplementary_specification_F5ACAA22.html" guid="{B16C2941-791C-44E6-B353-354109B5C9DE}">补充规约</a>可封装在一起，来为特定的“特性”或其他子系统分组定义<a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_software_requirements_specification_934E66F.html" guid="{BE8165DC-BAF2-4237-B27D-F2A037023364}">软件需求规约（SRS）</a>。<br />
    <br />
    所开发的系统越大、越复杂，就会出现越多的表达或需求类型，且需求量也越大。项目的“业务规则”和“愿景”陈述跟踪到“用户需要”、“特征”或其他“产品需求”。<a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_usecase_A5D30E62.html" guid="{B1526BC5-E346-42CB-A08A-3C0D7F382407}">用例</a>或其他形式的建模及其他<a class="elementLink" href="./../../../rup/workproducts/rup_supplementary_specification_F5ACAA22.html" guid="{B16C2941-791C-44E6-B353-354109B5C9DE}">补充规约</a>可驱动设计需求，这些需求又可进一步分解为功能和非功能“软件需求”，如“分析与设计”模型和图中所示。
</p>
<h3>
    <a id="MoreInfo" name="MoreInfo">更多信息</a>
</h3>
<p>
    可在以下部分找到关于此主题的更多信息：
</p>
<p>
    <a class="elementLinkWithType" href="./../../../rup/guidances/concepts/requirements_62E28784.html" guid="4.582668643506599E-305">Concept: 需求</a><br />
    <a class="elementLinkWithType" href="./../../../rup/guidances/concepts/requirements_management_8067CA83.html" guid="8.93441552545224E-307">Concept: 需求管理</a><br />
    <a class="elementLinkWithType" href="./../../../rup/guidances/concepts/traceability_8F6B898D.html" guid="1.4005695544042474E-306">Concept: 可跟踪性</a><br />
    <a class="elementLinkWithType" href="./../../../rup/guidances/whitepapers/applying_requirements_management_with_use_cases_A431D8A1.html" guid="1.4430543155816335E-305">Whitepaper: 使用用例应用需求管理</a>
</p><br />
<br /></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script type="text/javascript" language="JavaScript">
				contentPage.onload();
			</script>
</html>
